packages/core/src/delegation/delegation-revocation.ts:105

• The assertion message and validation in postRevocation are outdated after the config refactor: it checks truveraApiConfigs but the error message still mentions truveraApiSponsorKey, and it doesn't validate required fields (authKey, apiUrl). This can lead to confusing errors later (e.g., building a URL with undefined).

  assert(!!ctx.truveraApiConfigs, 'truveraApiSponsorKey is required');
  const jwt = await signRevocationJWT(ctx, {registryId, ...body});

packages/core/src/delegation/delegation-offer.ts:380

• New behavior is introduced here (building revocationContext from wallet.dataStore.configs.truveraApi and passing it into delegated issuance), but there’s no test coverage asserting that the handler includes revocation context when configs are present (and omits it when absent). Adding a unit test around DELEGATION_REQUEST_HANDLER (or an integration test for the offer->issue flow) would prevent regressions in the config plumbing.

      revocationContext: {
        wallet,
        truveraApiConfigs: wallet.dataStore.configs.truveraApi,
        issuerDID: delegationOffer.issuerDID || issuerDID,
      },